Network optimization and control for wireless networks

ABSTRACT

The disclosed technology is generally directed towards optimization and control of wireless networks based on monitoring and/or analytics data received at a radio access network (RAN) controller device in a split RAN protocol architecture. The RAN controller device processes the monitoring/analytics data and provides control information and/or optimization data, which can be policy data, to a central unit device that can configure the wireless network based on the control information and/or optimization data. The technology can facilitate optimization and configuration of mobility procedures including handovers and secondary cell group changes, optimization of carrier aggregation and dual connectivity procedures based on multiple metrics, and can facilitate centralized optimization of topology and route selection for integrated access and backhaul nodes.

CROSS-REFERENCE TO RELATED APPLICATIONS

The subject patent application is a continuation of, and claims priorityto, U.S. patent application Ser. No. 16/282,800, filed Feb. 22, 2019,and entitled “NETWORK OPTIMIZATION AND CONTROL FOR WIRELESS NETWORKS”,which applications claim priority to U.S. Provisional Patent ApplicationNo. 62/760,029, filed on Nov. 12, 2018 entitled “NETWORK OPTIMIZATIONAND CONTROL FOR 5G NETWORKS”, the entireties of which applications arehereby incorporated by reference herein.

TECHNICAL FIELD

The present application relates generally to the field of mobilecommunications, and more particularly to enabling mobility, dualconnectivity, and backhaul routing optimization using a radio accessnetwork controller in an advanced wireless network.

BACKGROUND

To meet the huge demand for data centric applications, Third GenerationPartnership Project (3GPP) systems and systems that employ one or moreaspects of the specifications of the Fourth Generation (4G) standard forwireless communications will be extended to a Fifth Generation (5G)standard for wireless communications. Challenges exist with respect toproviding levels of service associated with forthcoming 5G and othernext generation network standards.

BRIEF DESCRIPTION OF THE DRAWINGS

Non-limiting and non-exhaustive embodiments of the subject disclosureare described with reference to the following figures, wherein likereference numerals refer to like parts throughout the various viewsunless otherwise specified.

FIG. 1 illustrates an example wireless communication system, inaccordance with various aspects and embodiments of the subjectdisclosure.

FIG. 2 illustrates an example block diagram of a split architecturenetwork with a radio access network controller, in accordance withvarious aspects and embodiments of the subject disclosure.

FIG. 3 illustrates an example block diagram of a radio access networkcontroller, in accordance with various aspects and embodiments of thesubject disclosure.

FIG. 4 illustrates an example block diagram representing integratedaccess and backhaul network topology and routing, in accordance withvarious aspects and embodiments of the subject disclosure.

FIG. 5 illustrates an example block diagram representing integratedaccess and backhaul network topology and re-routing of traffic, inaccordance with various aspects and embodiments of the subjectdisclosure.

FIG. 6 illustrates example operations for generating control informationin a radio access network controller for use in configuration of theradio access network, in accordance with various aspects and embodimentsof the subject disclosure.

FIG. 7 illustrates example operations for optimizing a wireless networkbased on received monitoring data, in accordance with various aspectsand embodiments of the subject disclosure.

FIG. 8 illustrates example operations for optimizing a wireless networkbased on received analytics data, in accordance with various aspects andembodiments of the subject disclosure.

FIG. 9 illustrates an example block diagram of a non-limiting embodimentof a mobile network platform, in accordance with various aspectsdescribed herein.

FIG. 10 illustrates an example block diagram of a computer that can beoperable to execute processes and methods, in accordance with variousaspects and embodiments of the subject disclosure.

DETAILED DESCRIPTION

Various embodiments of the technology disclosed herein are directedtowards facilitating mobility, dual-connectivity, and backhaul routingoptimization using a Radio Access Network (RAN) controller that caninterface with the network and use radio measurements and other metricsand analytics to optimize RAN performance. Note that as used herein, theterms “optimize,” “optimization” and “optimizing” do not necessarilymean actually ideal, but rather can be interpreted as moving towards amore optimal state.

As will be understood, the technology the RAN Controller can be used tooptimize RAN operation in different scenarios, including to directly orindirectly influence or control the operation of the Central Unit (CU)and underlying protocol layers, including procedures involving radioresource control (RRC) signaling. Example, non-limiting scenariosinclude mobility/radio resource management (RRM); carrieraggregation/dual connectivity (CA/DC) addition/removal; and integratedaccess and backhaul (IAB) topology formation and routing updates.

One or more embodiments are now described with reference to thedrawings, wherein like reference numerals are used to refer to likeelements throughout. In the following description, for purposes ofexplanation, numerous specific details are set forth in order to providea thorough understanding of the various embodiments. It is evident,however, that the various embodiments can be practiced without thesespecific details (and without applying to any particular networkedenvironment or standard).

As used in this disclosure, in some embodiments, the terms “component,”“system” and the like are intended to refer to, or comprise, acomputer-related entity or an entity related to an operational apparatuswith one or more specific functionalities, wherein the entity can beeither hardware, a combination of hardware and software, software, orsoftware in execution. As an example, a component may be, but is notlimited to being, a process running on a processor, a processor, anobject, an executable, a thread of execution, computer-executableinstructions, a program, and/or a computer. By way of illustration andnot limitation, both an application running on a server and the servercan be a component.

One or more components may reside within a process and/or thread ofexecution and a component may be localized on one computer and/ordistributed between two or more computers. In addition, these componentscan execute from various computer readable media having various datastructures stored thereon. The components may communicate via localand/or remote processes such as in accordance with a signal having oneor more data packets (e.g., data from one component interacting withanother component in a local system, distributed system, and/or across anetwork such as the Internet with other systems via the signal). Asanother example, a component can be an apparatus with specificfunctionality provided by mechanical parts operated by electric orelectronic circuitry, which is operated by a software application orfirmware application executed by a processor, wherein the processor canbe internal or external to the apparatus and executes at least a part ofthe software or firmware application. As yet another example, acomponent can be an apparatus that provides specific functionalitythrough electronic components without mechanical parts, the electroniccomponents can comprise a processor therein to execute software orfirmware that confers at least in part the functionality of theelectronic components. While various components have been illustrated asseparate components, it will be appreciated that multiple components canbe implemented as a single component, or a single component can beimplemented as multiple components, without departing from exampleembodiments.

Further, the various embodiments can be implemented as a method,apparatus or article of manufacture using standard programming and/orengineering techniques to produce software, firmware, hardware or anycombination thereof to control a computer to implement the disclosedsubject matter. The term “article of manufacture” as used herein isintended to encompass a computer program accessible from anycomputer-readable (or machine-readable) device or computer-readable (ormachine-readable) storage/communications media. For example, computerreadable storage media can comprise, but are not limited to, magneticstorage devices (e.g., hard disk, floppy disk, magnetic strips), opticaldisks (e.g., compact disk (CD), digital versatile disk (DVD)), smartcards, and flash memory devices (e.g., card, stick, key drive). Ofcourse, those skilled in the art will recognize many modifications canbe made to this configuration without departing from the scope or spiritof the various embodiments.

Moreover, terms such as “mobile device equipment,” “mobile station,”“mobile,” subscriber station,” “access terminal,” “terminal,” “handset,”“communication device,” “mobile device” (and/or terms representingsimilar terminology) can refer to a wireless device utilized by asubscriber or mobile device of a wireless communication service toreceive or convey data, control, voice, video, sound, gaming orsubstantially any data-stream or signaling-stream. The foregoing termsare utilized interchangeably herein and with reference to the relateddrawings. Likewise, the terms “access point (AP),” “Base Station (BS),”BS transceiver, BS device, cell site, cell site device, “gNode B (gNB),”“evolved Node B (eNode B),” “home Node B (HNB)” and the like, areutilized interchangeably in the application, and refer to a wirelessnetwork component or appliance that transmits and/or receives data,control, voice, video, sound, gaming or substantially any data-stream orsignaling-stream from one or more subscriber stations. Data andsignaling streams can be packetized or frame-based flows.

Furthermore, the terms “device,” “communication device,” “mobiledevice,” “subscriber,” “customer entity,” “consumer,” “customer entity,”“entity” and the like are employed interchangeably throughout, unlesscontext warrants particular distinctions among the terms. It should beappreciated that such terms can refer to human entities or automatedcomponents supported through artificial intelligence (e.g., a capacityto make inference based on complex mathematical formalisms), which canprovide simulated vision, sound recognition and so forth.

Embodiments described herein can be exploited in substantially anywireless communication technology, comprising, but not limited to,wireless fidelity (Wi-Fi), global system for mobile communications(GSM), universal mobile telecommunications system (UMTS), worldwideinteroperability for microwave access (WiMAX), enhanced general packetradio service (enhanced GPRS), third generation partnership project(3GPP) long term evolution (LTE), third generation partnership project 2(3GPP2) ultra mobile broadband (UMB), high speed packet access (HSPA),Z-Wave, Zigbee and other 802.XX wireless technologies and/or legacytelecommunication technologies.

FIG. 1 illustrates an example wireless communication system 100 inaccordance with various aspects and embodiments of the subjectdisclosure. In one or more embodiments, system 100 can comprise one ormore user equipment UEs 104 and 102, which can have one or more antennapanels having vertical and horizontal elements. A UE 102 can be a mobiledevice such as a cellular phone, a smartphone, a tablet computer, awearable device, a virtual reality (VR) device, a heads-up display (HUD)device, a smart car, a machine-type communication (MTC) device, and thelike. UE 102 can also refer to any type of wireless device thatcommunicates with a radio network node in a cellular or mobilecommunication system. Examples of UE 102 are target device, device todevice (D2D) UE, machine type UE or UE capable of machine to machine(M2M) communication, PDA, Tablet, mobile terminals, smart phone, laptopembedded equipped (LEE), laptop mounted equipment (LME), USB donglesetc. User equipment UE 102 can also comprise IOT devices thatcommunicate wirelessly. In various embodiments, system 100 is orcomprises a wireless communication network serviced by one or morewireless communication network providers. In example embodiments, a UE102 can be communicatively coupled to the wireless communication networkvia a network node 106.

The non-limiting term network node (or radio network node) is usedherein to refer to any type of network node serving a UE 102 and UE 104and/or connected to other network node, network element, or anothernetwork node from which the UE 102 or 104 can receive a radio signal.Network nodes can also have multiple antennas for performing varioustransmission operations (e.g., MIMO operations). A network node can havea cabinet and other protected enclosures, an antenna mast, and actualantennas. Network nodes can serve several cells, also called sectors,depending on the configuration and type of antenna. Examples of networknodes (e.g., network node 106) can comprise but are not limited to:NodeB devices, base station (BS) devices, access point (AP) devices, andradio access network (RAN) devices. The network node 106 can alsocomprise multi-standard radio (MSR) radio node devices, including butnot limited to: an MSR BS, an eNode B, a network controller, a radionetwork controller (RNC), a base station controller (BSC), a relay, adonor node controlling relay, a base transceiver station (BTS), atransmission point, a transmission node, an RRU, an RRH, nodes indistributed antenna system (DAS), and the like. In 5G terminology, thenode 106 can be referred to as a gNodeB device.

Wireless communication system 100 can employ various cellulartechnologies and modulation schemes to facilitate wireless radiocommunications between devices (e.g., the UE 102 and 104 and the networknode 106). For example, system 100 can operate in accordance with aUMTS, long term evolution (LTE), high speed packet access (HSPA), codedivision multiple access (CDMA), time division multiple access (TDMA),frequency division multiple access (FDMA), multi-carrier code divisionmultiple access (MC-CDMA), single-carrier code division multiple access(SC-CDMA), single-carrier FDMA (SC-FDMA), OFDM, (DFT)-spread OFDM orSC-FDMA)), FBMC, ZT DFT-s-OFDM, GFDM, UFMC, UW DFT-Spread-OFDM, UW-OFDM,CP-OFDM, resource-block-filtered OFDM, and UFMC. However, variousfeatures and functionalities of system 100 are particularly describedwherein the devices (e.g., the UEs 102 and 104 and the network device106) of system 100 are configured to communicate wireless signals usingone or more multi carrier modulation schemes, wherein data symbols canbe transmitted simultaneously over multiple frequency subcarriers (e.g.,OFDM, CP-OFDM, DFT-spread OFMD, UFMC, FMBC, etc.).

In various embodiments, system 100 can be configured to provide andemploy 5G wireless networking features and functionalities. 5G wirelesscommunication networks are expected to fulfill the demand ofexponentially increasing data traffic and to allow people and machinesto enjoy gigabit data rates with virtually zero latency. Compared to 4G,5G supports more diverse traffic scenarios. For example, in addition tothe various types of data communication between conventional UEs (e.g.,phones, smartphones, tablets, PCs, televisions, Internet enabledtelevisions, etc.) supported by 4G networks, 5G networks can be employedto support data communication between smart cars in association withdriverless car environments, as well as machine type communications(MTCs).

Turning now to FIG. 2, illustrated is an example block diagram of asplit architecture network with a radio access network controller inaccordance with various aspects and embodiments of the subjectdisclosure. More particularly, 5G networks or New Radio (NR) can bedeployed as a standalone (SA) radio access technology or as anon-standalone (NSA) radio access technology assisted by another radioaccess technology. 4G or Long Term Evolution (LTE), which is currentlydeployed, can provide seamless coverage and uninterrupted connectivity,however NR can provide increased data rates or new services but due tothe currently limited distribution, dual connectivity between LTE and NRis especially attractive for NSA NR because control plane functions canbe sent over LTE while the data plane transmissions can be mapped to NR,allowing for simplified early NR deployments where device support forboth LTE and NR is expected. Future deployments can migrate to astandalone NR operation as well, where control plane information is alsosent over NR. In an embodiment, the master cell group (MCG) bearerprovides control plane functionality is sent over LTE, while user planetraffic may be sent over both LTE and NR:

3GPP NR-based 5G mobile networks can be deployed using a split RANprotocol architecture such that on the user plane, the packet dataconvergence protocol (PDCP) sublayers can reside at a centralized unit(central unit/CU) device 202, while the RLC (radio link control), MAC(media access control), and PHY (physical) layers can reside at thedistributed unit (DU) device 204. The CU-UP (centralized unit-userplane) manages user plane data which is carried on Data Radio Bearers(DRB s) that traverse the above described user plane RAN protocolarchitecture. On the control plane, the CU-CP (centralized unit-controlplane) utilizes signaling radio bearers (SRBs) that are set up and carrycontrol messages from the RRC layer and which also utilize the packetdata convergence protocol (PDCP) layer at the centralized unit 202, andare further carried down through the RLC, MAC, and PHY layers at thedistributed unit 204 to be delivered to the UE over the air interface.Each network user can be allocated multiple DRBs and SRBs by thenetwork. The network interface between the centralized unit 202 anddistributed unit 204 can be called the F1 interface per 3GPPspecifications.

As described herein, the centralized unit 202 is connected to a RANcontroller (RC) 206 device such as shown in FIG. 2. The RAN controller206 can be provided with measurements, metrics, and other analytics 208(e.g., counters, statistics, messages) from the centralized unit 202,which can be then processed by the RAN controller 206 usingoptimization, machine learning, and other tools to determine policiesand procedures related to RRM, RRC which can be used to manage mobility,dual-connectivity, carrier aggregation, and IAB topology formation androuting. The measurements and other information from the centralizedunit 202 may be provided directly without processing at the centralizedunit 202, or may be aggregated, refined, and filtered at the centralizedunit 202, e.g., to reduce the signaling volume and simplify theprocessing at the RAN controller 206.

The RAN controller 206 can be physically separated or co-located withother RAN equipment, including the centralized unit 202 (CU-UP and/orCU-CP). The RAN controller 206 also may be a logical entity that isvirtualized to run on different hardware platforms in a flexible manner.The interface between the centralized unit 202 and RAN controller 206can be implemented according to a standardized open interface (e.g., E2interface) or over a proprietary interface with vendor/operator specificapplication protocol interfaces (APIs) defined to exchange theinformation between the centralized unit 202 and RAN controller 206according to the scenarios and algorithms supported.

In one example, the RAN controller 206 provides explicit RRC/F1information 210 elements to the centralized unit 202. Note that it isfeasible to directly pass the corresponding RRC/F1 messages 210 betweenthe centralized unit 202 to the RAN controller 206, however the volumeand frequency of those messages may include significant processing atthe RAN controller 206 and thus could place stringent requirements onthe throughput and latency of the CU-RC interface. Thus, in anotherexample the RAN controller 206 does not provide the explicit RRC/F1messages 210, but instead provides the information as policies governingthe configuration and operation of procedures at the centralized unit202, which implicitly indicates values or ranges of values for theRRC/F1 configurations from which the centralized unit 202 may select thevalues to provide to UEs or connected DUs (e.g., distributed unit 204).

Turning now to FIG. 3, illustrated is an example block diagram 300 ofthe radio access network controller 206 in accordance with variousaspects and embodiments of the subject disclosure. The radio accessnetwork controller 206 can comprise an optimization engine 302, whichcan incorporate or be coupled to a machine learning engine. Theoptimization engine 302 can facilitate operations of a mobility manager304, a multiconnectivity manager 306 to manage carrier aggregation/dualconnectivity addition/removal, and an IAB/topology/routing manager 308to manage the topology of the IAB network and optimize routing updates.

With regard to the mobility manager 304, for Eutra NR Dual Connectivity(EN-DC) and standalone mobility procedures, NR has defined a procedurecalled Reconfiguration-With-Sync, which includes both primary cell(PCell) handovers for master cell group (MCG) and PSCell addition/changeprocedures for secondary cell group (SCG) connectivity. To determinewhen to perform this procedure, the network may configure the UE toderive reference signal received power (RSRP), reference signal receivedquality (RSRQ) and signal-to-interference-plus-noise ratio (SINR)measurement results per reference signal (RS) index (e.g., SSB or CSI-RSbeam) or cell associated to NR measurement objects based on parametersconfigured in the RRC configured measurement object (e.g., maximumnumber of beams to be averaged and beam consolidation thresholds) and inthe RRC configured report config (including the reference signal type tobe measured, SS/PBCH block or channel state information-referencesignals (CSI-RS)). Both periodic and event-triggered measurements can beconfigured.

In case of event-triggered measurement reports, the RRC signalingspecifies criteria for triggering of an NR measurement reporting event.The criteria can include comparing the current serving cell to absolutethresholds, as well as comparing neighboring detected cells to servingcells with a relative offset or absolute threshold.

In addition, procedures such as conditional HO (handover) may besupported to enable the UE to initiate handover or secondary cell groupchange mobility procedures. In this case the network configures the UEwith the thresholds for measurement reporting, as well as informationcorresponding to when the UE can autonomously trigger the handover orsecondary cell group change.

The CU-RC interface (FIG. 2) may provide the following parameters to thecentralized unit 202 for controlling the UE mobility measurements viaRRC configuration: RS configuration (e.g., SMTC or SS/PBCH BlockMeasurement Time Configuration, set of CSI-RS RRM resources); EventThreshold; Hysteresis; Time-To-Trigger; Trigger Quantity (e.g., RSRP,RSRQ, SINR); and White Cell List (if used by the network), and possiblyothers.

In order to properly configure the measurement and reporting triggersand mobility procedure parameters, the algorithms and analyticsprocessing in the RAN controller 206 log the measurement reports fromUEs, and log the success/failure metrics associated with a given set ofparameters/reported metrics. For example, certain timers configured bythe network at the UE (e.g., T304) are also associated withReconfiguration-With-Sync procedures. In addition, the RAN controller206 may utilize data such as the number of successful random accessattempts on a target cell to tune a set of thresholds and timers.

Based on the measurements and analytics from the centralized unit 202,the RAN controller 206 can optimize different metrics related tomobility/RRM procedures, such as increasing the success rate of (e.g.,maximizing) the number of successful handover/secondary cell groupchange events, reducing or minimizing the number of failures, reducingthe interruption time during the Reconfiguration-With-Sync procedure,and/or creating policies governing when to trigger a handover orsecondary cell group change based on UE speed, location, device type, orQoS profile. Information about UE trajectory (speed, location, etc.) canbe provided from the centralized unit 202 based on RAN measurements, ormay be provided the RAN controller 206 by a location server/databasewhich obtains the information from application layer data from thedevices.

In addition to optimizing mobility procedures, the RAN controller 206can additionally utilize measurements and radio link failure (RLF)statistics from the centralized unit 202 to optimize and configuretimers/thresholds used for RLF procedures and radio link monitoring(RLM) resources and for both master cell group and secondary cell groupconnectivity legs.

The multiconnectivity manager 306 can facilitate optimization of singleconnectivity and dual connectivity. While activation/deactivation ofsecondary cells is a MAC-controlled procedure and may not be suitablefor the CU-RC interface (unless there is an additional interface fromthe RAN controller 206 to the distributed unit), the additional/removalof secondary cells is controlled by RRC at the centralized unit 202 andcan be based on multiple factors such as RRM measurements (e.g.,coverage relative to the primary cell), UE capabilities, QoS, andbearer-level traffic statistics. In addition, the configuration ofdiscontinuous reception (DRX) and measurement gaps can have a largeinfluence of the ability of the distributed unit scheduler to takeadvantage of channel-aware feedback and bursty traffic arrivals. In thisway, the RAN controller 206 can take these factors into account andprovide the secondary cell configurations to the centralized unit 202over the RC-CU interface.

For EN-DC or NR-NR DC, RRC, messages are exchanged between the mastereNB or gNB to request the SgNB to perform certain actions, e.g., toestablish, modify or release a secondary cell group. The message mayinclude additional information, e.g., to assist the SgNB to set thesecondary cell group configuration. The message can also be used by acentralized unit to request a distributed unit to perform certainactions, e.g., to establish, modify or release a main cell group orsecondary cell group. In addition to RRM-related configurations, fordual connectivity, bearer configurations and power sharing parametersalso can be configured, which can be according to policies at the RANcontroller 206 related to capacity, coverage, or UE power optimizationobjectives. When to add/remove a secondary gNB can be controlled by theRAN controller 206 over the RC-CU, either explicitly by providing theRRC messages to the centralized unit 202, or implicitly by providingpolicies to the centralized unit 202 governing the establishment ormodification of dual connectivity for a UE.

The IAB manager 308 can optimize routing and IAB topology for a network.An L2 multi-hop IAB architecture can be built on the basic CU-DU split.However, instead of having a single distributed unit, as shown in FIG. 4a combination of UE 404 and distributed units (e.g., 446 and 447) alongwith a donor distributed unit 448 can be cascaded to create a multi-hopnetwork. Similar to a CU-DU split, various functions such as RRC andPDCP for the UEs, including the UE-Fs of the distributed unit reside inthe centralized unit 202, which can be also referred to as the donor CU.

As shown in FIG. 4, in order to support the routing and forwarding ofpackets, a protocol stack layer, referred to as an “adaptation layer,”can be added above the RLC layer at the IAB nodes. The adaptation layers(446 a-447 a) may perform the tasks of routing of UE traffic across themulti-hop network, and performing an aggregation of bearers frommultiple UE into common backhaul bearers. More particularly, thisadaptation layer can be responsible for forwarding and routing oftraffic, as well as for multiplexing and de-multiplexing UE bearers witha single backhaul RLC channel (which can be referred to as an RLCchannel instead of a bearer, because PDCP may not be used on theintermediate nodes when relaying traffic). This also implies that routeswitching due to load balancing, in response to link blockage/failure,or in response to UE mobility can be handled below L3 (network layer 3),because the RRC anchor does not change and the procedures/signaling toaddress it can be contained within the RAN. This can be an additionalbenefit of utilizing the CU-DU split architecture for IAB, becausesupport for fast mobility and fast route update can include minimal RRCconfiguration changes.

The configuration of parameters for the IAB nodes to connect to eachother via topology adaptation and initiate route changes/selection canbe centrally managed at the donor CU or by the RAN controller 206. Inone example the construction of the topology graph of the set ofpossible connections between IAB nodes and donors may be performed bythe RAN controller 206, which can be a long-term decision that does notchange, while the selection of one or more routes to utilize for routinga given packet may be performed by the IAB node or IAB donor.

By way of example, FIG. 5 shows how one route for routing a given packetis changed to another route by routing through a relay distributed unit449 (with adaptation layer 449 a) instead of through the relaydistributed unit 447.

In one example, routing tables used at the adaptation layer to forwardcontrol plane and user plane traffic across one or more backhaul hopsmay be optimized based on RSRP/RSRQ RRM measurements made across IABnodes, cross-link interference measurements, traffic load, end-to-enduser or per-backhaul link throughput and latency, frame structure,access and backhaul multiplexing capabilities at the IAB node, andinformation about the IAB topology (e.g., number of connected child IABnodes or access UEs). The measurements/metrics from the centralized unit202 and topology and route selection parameters/policies from the RANcontroller 206 may be exchanged over the CU-RC interface. The RANcontroller 206 can additionally take into account information which maynot be available in the RAN or donor CU such as user location,application layer metrics, non-NR/3GPP traffic sent over backhaul links,and IAB node power consumption.

In another example, the RAN controller 206 provides the IAB topologymanager at the centralized unit 202 or donor node with policies andparameters to use when determining which IAB nodes to connect forbackhaul routing. For example the policies may indicate latency bounds,throughput ranges, serving cell or interference measurement thresholds,reliability targets, or minimum/maximum number of supportable downstreamchild nodes and/or access UEs.

In another example, the RAN controller 206 may be able to directlyobtain various radio measurements and scheduling/resource allocationmetrics directly from the IAB nodes via an interface between the RANcontroller 206 and IAB distributed units, which is tunneled over radiobearers managed at the donor CU. For example, if IP connectivity can besupported between the IAB node DUs and MTs (distributed unit function,and the mobile terminal function, which is the UE function within therelay node) and the RAN controller 206, the topology/routingoptimization functionality at the RAN controller 206 can directlyrequest update measurements/information from the IAB nodes via anapplication layer protocol instead of relying on RAN-defined signaling(e.g., RRC or F1 messages). This interface can also be used for remoteoperational management of the IAB nodes (e.g. IAB node hardware/softwarestatus and configuration of parameters which are not managed by thedonor CU)

One or more example aspects are represented in FIG. 6, and cancorrespond to a radio access network controller device comprising aprocessor and a memory that stores executable instructions that, whenexecuted by the processor, facilitate performance of operations and/orcomponents. Example operations comprise operation 602, which representsreceiving monitoring data from a central unit device of a split radioaccess network, wherein the monitoring data is associated with acommunication link between a distributed unit device of the split radioaccess network and a user equipment device. Operation 604 representsgenerating control information based on processing the monitoring data.Operation 606 represents communicating between the radio access networkcontroller device and the central unit device, comprising transmittingthe control information to the central unit device for use inconfiguration of the radio access network.

Generating the control information based on the processing themonitoring data can comprise determining policy data for transmitting asthe control information to the central unit device. Generating thecontrol information can comprise generating a radio resource controlinformation element, and the transmitting the control information to thecentral unit device can comprise transmitting a message comprising theradio resource control information element.

Generating the control information based on the processing themonitoring data can comprise generating optimization data configured tooptimize the communication link based on an analysis of the monitoringdata.

Generating the control information based on the processing themonitoring data can comprise generating at least one of: firstoptimization data to increase a success rate of handover events, orsecond optimization data to increase a success rate of secondary cellgroup change events. Generating the control information based on theprocessing the monitoring data can comprise determining an addition or aremoval of a secondary cell associated with the user equipment device.Generating the control information based on the processing themonitoring data can comprise determining a topology for integratedaccess and backhaul nodes.

The distributed unit can comprise an integrated access and backhaulnode, and wherein the generating the control information based on theprocessing the monitoring data can comprise selecting a route fortraffic between the user equipment and the integrated access andbackhaul node.

One or more aspects, such as those implemented in example operations ofa method, are shown in FIG. 7 in accordance with various aspects andembodiments of the subject disclosure. Operation 702 representsreceiving, by a network device of a wireless network and comprising aprocessor, monitoring data from a central unit device of a split radioaccess network, wherein the monitoring data is associated with acommunication link between a distributed unit device of the split radioaccess network and a user equipment device. Operation 704 representsgenerating, by the network device, optimization data based on ananalysis of the monitoring data, wherein the optimization data isconfigured to optimize the communication link. Operation 706 representstransmitting, by the network device, the optimization data to thecentral unit device.

Receiving the monitoring data can comprise receiving at least one of:measurement data, metric data, counter data, statistics data, or messagedata. Receiving the monitoring data can comprise receiving themonitoring data as pre-processed data by the central unit device.

Generating the optimization data can comprise generating radio resourcecontrol data for use in configuring the distributed unit device.Generating the optimization data can comprise generating policy data foruse by the central unit device in configuration of the communicationlink. Generating the optimization data can comprise generating at leastone of: radio resource management data, machine learning data or routingdata.

Generating the optimization data can comprise generating at least oneof: first optimization data to increase a success rate of handoverevents, or second optimization data to increase a success rate ofsecondary cell group change events. Generating the optimization data cancomprise determining an addition or a removal of a secondary cellassociated with the user equipment device. Generating the optimizationdata can comprise determining a topology for integrated access andbackhaul nodes.

One or more aspects, such as implemented in a machine-readable storagemedium, comprising executable instructions that, when executed by aprocessor, facilitate performance of operations, are represented in FIG.8. Example operations comprise operation 802, which represents receivinganalytics data from a central unit device of a split radio accessnetwork, wherein the analytics data is associated with a communicationlink between a distributed unit device of the split radio access networkand a user equipment device. Operation 804 represents generatingoptimization data based on an analysis of the monitoring data, whereinthe optimization data is configured to optimize the communication link.Operation 806 represents transmitting the optimization data to thecentral unit device.

Generating the optimization data can comprise generating at least oneof: dual connectivity control information associated with the userequipment, or mobility procedure control information associated with theuser equipment. The distributed unit can comprise an integrated accessand backhaul node, and the generating the optimization data can compriseselecting a route for traffic between the user equipment and theintegrated access and backhaul node.

As can be seen, the technology described herein facilitates optimizationand configuration of mobility procedures including handovers and/orsecondary cell group changes for both standalone and non-standaloneoperation of NR networks. The technology described herein facilitatesoptimization of carrier aggregation and dual connectivity procedures andconfigurations based on multiple metrics including capacity, coverage,and UE power consumption. The technology described herein facilitatescentralized optimization of topology and route selection for IAB nodeswhich can operate using RAN-centric or IP-based signaling

FIG. 9 presents an example embodiment 900 of a mobile network platform910 that can implement and exploit one or more aspects of the disclosedsubject matter described herein. Generally, wireless network platform910 can include components, e.g., nodes, gateways, interfaces, servers,or disparate platforms, that facilitate both packet-switched (PS) (e.g.,internet protocol (IP), frame relay, asynchronous transfer mode (ATM)and circuit-switched (CS) traffic (e.g., voice and data), as well ascontrol generation for networked wireless telecommunication. As anon-limiting example, wireless network platform 910 can be included intelecommunications carrier networks, and can be considered carrier-sidecomponents as discussed elsewhere herein. Mobile network platform 910includes CS gateway node(s) 912 which can interface CS traffic receivedfrom legacy networks like telephony network(s) 940 (e.g., publicswitched telephone network (PSTN), or public land mobile network (PLMN))or a signaling system #7 (SS7) network 960. Circuit switched gatewaynode(s) 912 can authorize and authenticate traffic (e.g., voice) arisingfrom such networks. Additionally, CS gateway node(s) 912 can accessmobility, or roaming, data generated through SS7 network 960; forinstance, mobility data stored in a visited location register (VLR),which can reside in memory 930. Moreover, CS gateway node(s) 912interfaces CS-based traffic and signaling and PS gateway node(s) 918. Asan example, in a 3GPP UMTS network, CS gateway node(s) 912 can berealized at least in part in gateway GPRS support node(s) (GGSN). Itshould be appreciated that functionality and specific operation of CSgateway node(s) 912, PS gateway node(s) 918, and serving node(s) 916, isprovided and dictated by radio technology(ies) utilized by mobilenetwork platform 910 for telecommunication. Mobile network platform 910can also include the MMEs, HSS/PCRFs, SGWs, and PGWs disclosed herein.

In addition to receiving and processing CS-switched traffic andsignaling, PS gateway node(s) 918 can authorize and authenticatePS-based data sessions with served mobile devices. Data sessions caninclude traffic, or content(s), exchanged with networks external to thewireless network platform 910, like wide area network(s) (WANs) 950,enterprise network(s) 970, and service network(s) 980, which can beembodied in local area network(s) (LANs), can also be interfaced withmobile network platform 910 through PS gateway node(s) 918. It is to benoted that WANs 950 and enterprise network(s) 970 can embody, at leastin part, a service network(s) like IP multimedia subsystem (IMS). Basedon radio technology layer(s) available in technology resource(s) 917,packet-switched gateway node(s) 918 can generate packet data protocolcontexts when a data session is established; other data structures thatfacilitate routing of packetized data also can be generated. To thatend, in an aspect, PS gateway node(s) 918 can include a tunnel interface(e.g., tunnel termination gateway (TTG) in 3GPP UMTS network(s) (notshown)) which can facilitate packetized communication with disparatewireless network(s), such as Wi-Fi networks.

In embodiment 900, wireless network platform 910 also includes servingnode(s) 916 that, based upon available radio technology layer(s) withintechnology resource(s) 917, convey the various packetized flows of datastreams received through PS gateway node(s) 918. It is to be noted thatfor technology resource(s) 917 that rely primarily on CS communication,server node(s) can deliver traffic without reliance on PS gatewaynode(s) 918; for example, server node(s) can embody at least in part amobile switching center. As an example, in a 3GPP UMTS network, servingnode(s) 916 can be embodied in serving GPRS support node(s) (SGSN).

For radio technologies that exploit packetized communication, server(s)914 in wireless network platform 910 can execute numerous applicationsthat can generate multiple disparate packetized data streams or flows,and manage (e.g., schedule, queue, format . . . ) such flows. Suchapplication(s) can include add-on features to standard services (forexample, provisioning, billing, customer support . . . ) provided bywireless network platform 910. Data streams (e.g., content(s) that arepart of a voice call or data session) can be conveyed to PS gatewaynode(s) 918 for authorization/authentication and initiation of a datasession, and to serving node(s) 916 for communication thereafter. Inaddition to application server, server(s) 914 can include utilityserver(s), a utility server can include a provisioning server, anoperations and maintenance server, a security server that can implementat least in part a certificate authority and firewalls as well as othersecurity mechanisms, and the like. In an aspect, security server(s)secure communication served through wireless network platform 910 toensure network's operation and data integrity in addition toauthorization and authentication procedures that CS gateway node(s) 912and PS gateway node(s) 918 can enact. Moreover, provisioning server(s)can provision services from external network(s) like networks operatedby a disparate service provider; for instance, WAN 950 or GlobalPositioning System (GPS) network(s) (not shown). Provisioning server(s)can also provision coverage through networks associated to wirelessnetwork platform 910 (e.g., deployed and operated by the same serviceprovider), such as femto-cell network(s) (not shown) that enhancewireless service coverage within indoor confined spaces and offload RANresources in order to enhance subscriber service experience within ahome or business environment by way of UE 975.

It is to be noted that server(s) 914 can include one or more processorsconfigured to confer at least in part the functionality of macro networkplatform 910. To that end, the one or more processor can execute codeinstructions stored in memory 930, for example. It is should beappreciated that server(s) 914 can include a content manager 915, whichoperates in substantially the same manner as described hereinbefore.

In example embodiment 900, memory 930 can store information related tooperation of wireless network platform 910. Other operationalinformation can include provisioning information of mobile devicesserved through wireless platform network 910, subscriber databases;application intelligence, pricing schemes, e.g., promotional rates,flat-rate programs, couponing campaigns; technical specification(s)consistent with telecommunication protocols for operation of disparateradio, or wireless, technology layers; and so forth. Memory 930 can alsostore information from at least one of telephony network(s) 940, WAN950, enterprise network(s) 970, or SS7 network 960. In an aspect, memory930 can be, for example, accessed as part of a data store component oras a remotely connected memory store.

Referring now to FIG. 10, there is illustrated a block diagram of acomputer 1000 operable to execute the functions and operations performedin the described example embodiments. The computer 1000 can providenetworking and communication capabilities between a wired or wirelesscommunication network and a server and/or communication device. In orderto provide additional context for various aspects thereof, the followingdiscussion are intended to provide a brief, general description of asuitable computing environment in which the various aspects of theembodiments can be implemented to facilitate the establishment of atransaction between an entity and a third party. While the descriptionabove is in the general context of computer-executable instructions thatcan run on one or more computers, those skilled in the art willrecognize that the various embodiments also can be implemented incombination with other program modules and/or as a combination ofhardware and software.

Generally, program modules include routines, programs, components, datastructures, etc., that perform particular tasks or implement particularabstract data types. Moreover, those skilled in the art will appreciatethat the various methods can be practiced with other computer systemconfigurations, including single-processor or multiprocessor computersystems, minicomputers, mainframe computers, as well as personalcomputers, hand-held computing devices, microprocessor-based orprogrammable consumer electronics, and the like, each of which can beoperatively coupled to one or more associated devices.

The illustrated aspects of the various embodiments can also be practicedin distributed computing environments where certain tasks are performedby remote processing devices that are linked through a communicationsnetwork. In a distributed computing environment, program modules can belocated in both local and remote memory storage devices.

Computing devices typically include a variety of media, which caninclude computer-readable storage media or communications media, whichtwo terms are used herein differently from one another as follows.

Computer-readable storage media can be any available storage media thatcan be accessed by the computer and includes both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structureddata, or unstructured data. Computer-readable storage media can include,but are not limited to, RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile disk (DVD) or other optical diskstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, or other tangible and/or non-transitorymedia which can be used to store desired information. Computer-readablestorage media can be accessed by one or more local or remote computingdevices, e.g., via access requests, queries or other data retrievalprotocols, for a variety of operations with respect to the informationstored by the medium.

Communications media can embody computer-readable instructions, datastructures, program modules or other structured or unstructured data ina data signal such as a modulated data signal, e.g., a carrier wave orother transport mechanism, and includes any information delivery ortransport media. The term “modulated data signal” or signals refers to asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in one or more signals. By way ofexample, and not limitation, communication media include wired media,such as a wired network or direct-wired connection, and wireless mediasuch as acoustic, RF, infrared and other wireless media.

Referring now to FIG. 10, there is illustrated a block diagram of acomputer 1000 operable to execute the functions and operations performedin the described example embodiments. For example, a network node (e.g.,network node 106) may contain components as described in FIG. 10. Thecomputer 1000 can provide networking and communication capabilitiesbetween a wired or wireless communication network and a server and/orcommunication device. In order to provide additional context for variousaspects thereof, FIG. 10 and the following discussion are intended toprovide a brief, general description of a suitable computing environmentin which the various aspects of the embodiments can be implemented tofacilitate the establishment of a transaction between an entity and athird party. While the description above is in the general context ofcomputer-executable instructions that can run on one or more computers,those skilled in the art will recognize that the various embodimentsalso can be implemented in combination with other program modules and/oras a combination of hardware and software.

Generally, program modules include routines, programs, components, datastructures, etc., that perform particular tasks or implement particularabstract data types. Moreover, those skilled in the art will appreciatethat the inventive methods can be practiced with other computer systemconfigurations, including single-processor or multiprocessor computersystems, minicomputers, mainframe computers, as well as personalcomputers, hand-held computing devices, microprocessor-based orprogrammable consumer electronics, and the like, each of which can beoperatively coupled to one or more associated devices.

The illustrated aspects of the various embodiments can also be practicedin distributed computing environments where certain tasks are performedby remote processing devices that are linked through a communicationsnetwork. In a distributed computing environment, program modules can belocated in both local and remote memory storage devices.

Computing devices typically include a variety of media, which caninclude computer-readable storage media or communications media, whichtwo terms are used herein differently from one another as follows.

Computer-readable storage media can be any available storage media thatcan be accessed by the computer and includes both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structureddata, or unstructured data. Computer-readable storage media can include,but are not limited to, RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile disk (DVD) or other optical diskstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, or other tangible and/or non-transitorymedia which can be used to store desired information. Computer-readablestorage media can be accessed by one or more local or remote computingdevices, e.g., via access requests, queries or other data retrievalprotocols, for a variety of operations with respect to the informationstored by the medium.

Communications media can embody computer-readable instructions, datastructures, program modules or other structured or unstructured data ina data signal such as a modulated data signal, e.g., a carrier wave orother transport mechanism, and includes any information delivery ortransport media. The term “modulated data signal” or signals refers to asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in one or more signals. By way ofexample, and not limitation, communication media include wired media,such as a wired network or direct-wired connection, and wireless mediasuch as acoustic, RF, infrared and other wireless media.

With reference to FIG. 10, implementing various aspects described hereinwith regards to the end-user device can include a computer 1000, thecomputer 1000 including a processing unit 1004, a system memory 1006 anda system bus 1008. The system bus 1008 couples system componentsincluding, but not limited to, the system memory 1006 to the processingunit 1004. The processing unit 1004 can be any of various commerciallyavailable processors. Dual microprocessors and other multi-processorarchitectures can also be employed as the processing unit 1004.

The system bus 1008 can be any of several types of bus structure thatcan further interconnect to a memory bus (with or without a memorycontroller), a peripheral bus, and a local bus using any of a variety ofcommercially available bus architectures. The system memory 1006includes read-only memory (ROM) 1027 and random access memory (RAM)1012. A basic input/output system (BIOS) is stored in a non-volatilememory 1027 such as ROM, EPROM, EEPROM, which BIOS contains the basicroutines that help to transfer information between elements within thecomputer 1000, such as during start-up. The RAM 1012 can also include ahigh-speed RAM such as static RAM for caching data.

The computer 1000 further includes an internal hard disk drive (HDD)1014 (e.g., EIDE, SATA), which internal hard disk drive 1014 can also beconfigured for external use in a suitable chassis (not shown), amagnetic floppy disk drive (FDD) 1016, (e.g., to read from or write to aremovable diskette 1018) and an optical disk drive 1020, (e.g., readinga CD-ROM disk 1022 or, to read from or write to other high capacityoptical media such as the DVD). The hard disk drive 1014, magnetic diskdrive 1016 and optical disk drive 1020 can be connected to the systembus 1008 by a hard disk drive interface 1024, a magnetic disk driveinterface 1026 and an optical drive interface 1028, respectively. Theinterface 1024 for external drive implementations includes at least oneor both of Universal Serial Bus (USB) and IEEE 1394 interfacetechnologies. Other external drive connection technologies are withincontemplation of the subject embodiments.

The drives and their associated computer-readable media providenonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For the computer 1000 the drives and mediaaccommodate the storage of any data in a suitable digital format.Although the description of computer-readable media above refers to aHDD, a removable magnetic diskette, and a removable optical media suchas a CD or DVD, it should be appreciated by those skilled in the artthat other types of media which are readable by a computer 1000, such aszip drives, magnetic cassettes, flash memory cards, cartridges, and thelike, can also be used in the example operating environment, andfurther, that any such media can contain computer-executableinstructions for performing the methods of the disclosed embodiments.

A number of program modules can be stored in the drives and RAM 1012,including an operating system 1030, one or more application programs1032, other program modules 1034 and program data 1036. All or portionsof the operating system, applications, modules, and/or data can also becached in the RAM 1012. It is to be appreciated that the variousembodiments can be implemented with various commercially availableoperating systems or combinations of operating systems.

A user can enter commands and information into the computer 1000 throughone or more wired/wireless input devices, e.g., a keyboard 1038 and apointing device, such as a mouse 1040. Other input devices (not shown)may include a microphone, an IR remote control, a joystick, a game pad,a stylus pen, touch screen, or the like. These and other input devicesare often connected to the processing unit 1004 through an input deviceinterface 1042 that is coupled to the system bus 1008, but can beconnected by other interfaces, such as a parallel port, an IEEE 1394serial port, a game port, a USB port, an IR interface, etc.

A monitor 1044 or other type of display device is also connected to thesystem bus 1008 through an interface, such as a video adapter 1046. Inaddition to the monitor 1044, a computer 1000 typically includes otherperipheral output devices (not shown), such as speakers, printers, etc.

The computer 1000 can operate in a networked environment using logicalconnections by wired and/or wireless communications to one or moreremote computers, such as a remote computer(s) 1048. The remotecomputer(s) 1048 can be a workstation, a server computer, a router, apersonal computer, portable computer, microprocessor-based entertainmentdevice, a peer device or other common network node, and typicallyincludes many or all of the elements described relative to the computer,although, for purposes of brevity, only a memory/storage device 1050 isillustrated. The logical connections depicted include wired/wirelessconnectivity to a local area network (LAN) 1052 and/or larger networks,e.g., a wide area network (WAN) 1054. Such LAN and WAN networkingenvironments are commonplace in offices and companies, and facilitateenterprise-wide computer networks, such as intranets, all of which mayconnect to a global communications network, e.g., the Internet.

When used in a LAN networking environment, the computer 1000 isconnected to the local network 1052 through a wired and/or wirelesscommunication network interface or adapter 1056. The adapter 1056 mayfacilitate wired or wireless communication to the LAN 1052, which mayalso include a wireless access point disposed thereon for communicatingwith the wireless adapter 1056.

When used in a WAN networking environment, the computer 1000 can includea modem 1058, or is connected to a communications server on the WAN1054, or has other means for establishing communications over the WAN1054, such as by way of the Internet. The modem 1058, which can beinternal or external and a wired or wireless device, is connected to thesystem bus 1008 through the input device interface 1042. In a networkedenvironment, program modules depicted relative to the computer, orportions thereof, can be stored in the remote memory/storage device1050. It will be appreciated that the network connections shown areexemplary and other means of establishing a communications link betweenthe computers can be used.

The computer is operable to communicate with any wireless devices orentities operatively disposed in wireless communication, e.g., aprinter, scanner, desktop and/or portable computer, portable dataassistant, communications satellite, any piece of equipment or locationassociated with a wirelessly detectable tag (e.g., a kiosk, news stand,restroom), and telephone. This includes at least Wi-Fi and Bluetooth™wireless technologies. Thus, the communication can be a predefinedstructure as with a conventional network or simply an ad hoccommunication between at least two devices.

Wi-Fi, or Wireless Fidelity, allows connection to the Internet from acouch at home, a bed in a hotel room, or a conference room at work,without wires. Wi-Fi is a wireless technology similar to that used in acell phone that enables such devices, e.g., computers, to send andreceive data indoors and out; anywhere within the range of a basestation. Wi-Fi networks use radio technologies called IEEE802.11 (a, b,g, n, etc.) to provide secure, reliable, fast wireless connectivity. AWi-Fi network can be used to connect computers to each other, to theInternet, and to wired networks (which use IEEE802.3 or Ethernet). Wi-Finetworks operate in the unlicensed 2.4 and 9 GHz radio bands, at an 11Mbps (802.11b) or 94 Mbps (802.11a) data rate, for example, or withproducts that contain both bands (dual band), so the networks canprovide real-world performance similar to the basic “10BaseT” wiredEthernet networks used in many offices.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit (ASIC), a digitalsignal processor (DSP), a field programmable gate array (FPGA), aprogrammable logic controller (PLC), a complex programmable logic device(CPLD), a discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. Processors can exploit nano-scale architectures suchas, but not limited to, molecular and quantum-dot based transistors,switches and gates, in order to optimize space usage or enhanceperformance of user equipment. A processor also can be implemented as acombination of computing processing units.

In the subject specification, terms such as “store,” “data store,” “datastorage,” “database,” “repository,” “queue”, and substantially any otherinformation storage component relevant to operation and functionality ofa component, refer to “memory components,” or entities embodied in a“memory” or components comprising the memory. It will be appreciatedthat the memory components described herein can be either volatilememory or nonvolatile memory, or can comprise both volatile andnonvolatile memory. In addition, memory components or memory elementscan be removable or stationary. Moreover, memory can be internal orexternal to a device or component, or removable or stationary. Memorycan comprise various types of media that are readable by a computer,such as hard-disc drives, zip drives, magnetic cassettes, flash memorycards or other types of memory cards, cartridges, or the like.

By way of illustration, and not limitation, nonvolatile memory cancomprise read only memory (ROM), programmable ROM (PROM), electricallyprogrammable ROM (EPROM), electrically erasable ROM (EEPROM), or flashmemory. Volatile memory can comprise random access memory (RAM), whichacts as external cache memory. By way of illustration and notlimitation, RAM is available in many forms such as synchronous RAM(SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rateSDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), anddirect Rambus RAM (DRRAM). Additionally, the disclosed memory componentsof systems or methods herein are intended to comprise, without beinglimited to comprising, these and any other suitable types of memory.

In particular and in regard to the various functions performed by theabove described components, devices, circuits, systems and the like, theterms (including a reference to a “means”) used to describe suchcomponents are intended to correspond, unless otherwise indicated, toany component which performs the specified function of the describedcomponent (e.g., a functional equivalent), even though not structurallyequivalent to the disclosed structure, which performs the function inthe herein illustrated example aspects of the embodiments. In thisregard, it will also be recognized that the embodiments comprise asystem as well as a computer-readable medium having computer-executableinstructions for performing the acts and/or events of the variousmethods.

Computing devices typically comprise a variety of media, which cancomprise computer-readable storage media and/or communications media,which two terms are used herein differently from one another as follows.Computer-readable storage media can be any available storage media thatcan be accessed by the computer and comprises both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structureddata, or unstructured data.

Computer-readable storage media can include, but are not limited to,random access memory (RAM), read only memory (ROM), electricallyerasable programmable read only memory (EEPROM), flash memory or othermemory technology, solid state drive (SSD) or other solid-state storagetechnology, compact disk read only memory (CD ROM), digital versatiledisk (DVD), Blu-ray disc or other optical disk storage, magneticcassettes, magnetic tape, magnetic disk storage or other magneticstorage devices or other tangible and/or non-transitory media which canbe used to store desired information.

In this regard, the terms “tangible” or “non-transitory” herein asapplied to storage, memory or computer-readable media, are to beunderstood to exclude only propagating transitory signals per se asmodifiers and do not relinquish rights to all standard storage, memoryor computer-readable media that are not only propagating transitorysignals per se. Computer-readable storage media can be accessed by oneor more local or remote computing devices, e.g., via access requests,queries or other data retrieval protocols, for a variety of operationswith respect to the information stored by the medium.

On the other hand, communications media typically embodycomputer-readable instructions, data structures, program modules orother structured or unstructured data in a data signal such as amodulated data signal, e.g., a carrier wave or other transportmechanism, and comprises any information delivery or transport media.The term “modulated data signal” or signals refers to a signal that hasone or more of its characteristics set or changed in such a manner as toencode information in one or more signals. By way of example, and notlimitation, communications media comprise wired media, such as a wirednetwork or direct-wired connection, and wireless media such as acoustic,RF, infrared and other wireless media

Further, terms like “user equipment,” “user device,” “mobile device,”“mobile,” station,” “access terminal,” “terminal,” “handset,” andsimilar terminology, generally refer to a wireless device utilized by asubscriber or user of a wireless communication network or service toreceive or convey data, control, voice, video, sound, gaming, orsubstantially any data-stream or signaling-stream. The foregoing termsare utilized interchangeably in the subject specification and relateddrawings. Likewise, the terms “access point,” “node B,” “base station,”“evolved Node B,” “cell,” “cell site,” and the like, can be utilizedinterchangeably in the subject application, and refer to a wirelessnetwork component or appliance that serves and receives data, control,voice, video, sound, gaming, or substantially any data-stream orsignaling-stream from a set of subscriber stations. Data and signalingstreams can be packetized or frame-based flows. It is noted that in thesubject specification and drawings, context or explicit distinctionprovides differentiation with respect to access points or base stationsthat serve and receive data from a mobile device in an outdoorenvironment, and access points or base stations that operate in aconfined, primarily indoor environment overlaid in an outdoor coveragearea. Data and signaling streams can be packetized or frame-based flows.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,” andthe like are employed interchangeably throughout the subjectspecification, unless context warrants particular distinction(s) amongthe terms. It should be appreciated that such terms can refer to humanentities, associated devices, or automated components supported throughartificial intelligence (e.g., a capacity to make inference based oncomplex mathematical formalisms) which can provide simulated vision,sound recognition and so forth. In addition, the terms “wirelessnetwork” and “network” are used interchangeable in the subjectapplication, when context wherein the term is utilized warrantsdistinction for clarity purposes such distinction is made explicit.

Moreover, the word “exemplary” is used herein to mean serving as anexample, instance, or illustration. Any aspect or design describedherein as “exemplary” is not necessarily to be construed as preferred oradvantageous over other aspects or designs. Rather, use of the wordexemplary is intended to present concepts in a concrete fashion. As usedin this application, the term “or” is intended to mean an inclusive “or”rather than an exclusive “or”. That is, unless specified otherwise, orclear from context, “X employs A or B” is intended to mean any of thenatural inclusive permutations. That is, if X employs A; X employs B; orX employs both A and B, then “X employs A or B” is satisfied under anyof the foregoing instances. In addition, the articles “a” and “an” asused in this application and the appended claims should generally beconstrued to mean “one or more” unless specified otherwise or clear fromcontext to be directed to a singular form.

In addition, while a particular feature may have been disclosed withrespect to only one of several implementations, such feature may becombined with one or more other features of the other implementations asmay be desired and advantageous for any given or particular application.Furthermore, to the extent that the terms “includes” and “including” andvariants thereof are used in either the detailed description or theclaims, these terms are intended to be inclusive in a manner similar tothe term “comprising.”

The above descriptions of various embodiments of the subject disclosureand corresponding figures and what is described in the Abstract, aredescribed herein for illustrative purposes, and are not intended to beexhaustive or to limit the disclosed embodiments to the precise formsdisclosed. It is to be understood that one of ordinary skill in the artmay recognize that other embodiments having modifications, permutations,combinations, and additions can be implemented for performing the same,similar, alternative, or substitute functions of the disclosed subjectmatter, and are therefore considered within the scope of thisdisclosure. Therefore, the disclosed subject matter should not belimited to any single embodiment described herein, but rather should beconstrued in breadth and scope in accordance with the claims below.

What is claimed is:
 1. A method, comprising: based on respective powerconsumption of integrated access and backhaul nodes associated with asplit radio access network, selecting, by network equipment comprising aprocessor, a route for traffic between a user equipment and adistributed unit device associated with the split radio access network;and based on the route, configuring, by the network equipment, acommunication link between the user equipment and the distributed unitdevice via the split radio access network.
 2. The method of claim 1,wherein selecting the route is further based on a location of the userequipment.
 3. The method of claim 1, wherein selecting the route isfurther based on an application layer metric.
 4. The method of claim 1,wherein selecting the route is further based on a latency threshold. 5.The method of claim 1, wherein selecting the route is further based onan interference measurement threshold.
 6. The method of claim 1, whereinthe route comprises a group of nodes of the integrated access andbackhaul nodes.
 7. The method of claim 1, wherein selecting the routecomprises generating a topology graph of possible connections betweenthe integrated access and backhaul nodes.
 8. Network equipment,comprising: a processor; and a memory that stores executableinstructions that, when executed by the processor, facilitateperformance of operations, comprising: choosing a route for trafficbetween a user equipment and a distributed unit device of a split radioaccess network based on respective power consumption of integratedaccess and backhaul nodes of the split radio access network; andforming, based on the route, a communication link, in the split radioaccess network, between the user equipment and the distributed unitdevice.
 9. The network equipment of claim 8, wherein the choosing isfurther based on a location of the user equipment.
 10. The networkequipment of claim 8, wherein the choosing is further based on anapplication layer metric.
 11. The network equipment of claim 8, whereinthe choosing is further based on a latency threshold.
 12. The networkequipment of claim 8, wherein the choosing is further based on aninterference measurement threshold.
 13. The network equipment of claim8, wherein the route comprises a group of the integrated access andbackhaul nodes.
 14. The network equipment of claim 8, wherein thechoosing comprises generating a topology graph of possible connectionsbetween at least two of the integrated access and backhaul nodes.
 15. Anon-transitory machine-readable medium, comprising executableinstructions that, when executed by a processor, facilitate performanceof operations, comprising: configuring a route for traffic between auser equipment and a distributed unit device that is part of a splitradio access network based on respective power consumption of integratedaccess and backhaul nodes that are part of the split radio accessnetwork; and establishing, based on the route via the split radio accessnetwork, a communication link between the user equipment and thedistributed unit device.
 16. The non-transitory machine-readable mediumof claim 15, wherein the configuring is further based on a location ofthe user equipment.
 17. The non-transitory machine-readable medium ofclaim 15, wherein the configuring is further based on an applicationlayer metric.
 18. The non-transitory machine-readable medium of claim15, wherein the configuring is further based on a latency threshold. 19.The non-transitory machine-readable medium of claim 15, wherein theconfiguring is further based on an interference measurement threshold.20. The non-transitory machine-readable medium of claim 15, wherein theroute comprises multiple nodes of the integrated access and backhaulnodes.